Clarification regarding Validation.Pattern #254
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ralfhandl
requested changes
May 8, 2024
There was a problem hiding this comment.
The current behavior is intended, Validation.Pattern is the counterpart to the JSON Schema keyword pattern, which explicitly states that
regular expressions are not implicitly anchored
If someone wants a prefix, suffix, or full match, they can anchor the regular expression using ^ and $, for example ^\d+$ will only match if the string consists entirely of digits and has a minimum length of 1.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The annotated property must match the regular expression in its entirety, because a regular expression like
\d+(one or more digits) is also matched by the string7up, just not in its entirety.